Q: 
How do I get remstud2 running at first time ?
A: 
Remstud2 works as a quake server. You run it with the proper parameters (see next question), and connect to it from a quake client. There are several commands assigned to impulses, you can run a .cfg script on the client to bind them to useful keyboard keys.

Q: 
How do I recam using remstud2 ?
A:
You do so by setting keypoints for the camera.
A keypoint is a point in 4-dimentional spacetime (or, more simply, point in space at a certain time, but it doesn't sound so cool). 
First you set one keypoint for the very first frame (typically pointing at player spawn spot). Then you move to the next shot, and run a playback of the demo. Once the player have reached the spot, you pause the demo, adjust the position and time slightly, and put another keypoint. You can go back to the first keypont, and preview this segment of camera movement from one point to another. If you are not unhappy, you can either add an extra camera point in between, or alter one of the original ones. Repeat the process till the very end of the demo.

Q: 
How do I stop editing and save my work ?
A: 
You just use the client to disconnect from the server.
If you provided a name for the output file, it will be generated, and you'll be able to play it from the same client.

Q: 
What are the command line parameters ?
A: 
There are two mandatory parmeters: name of the source demo that will be recammed, and the script file (typically with .rs2 extention).
If the script already exists it will be loaded, otherwise a new one will be created.
If you wish the recamming output to be available as a regular .dem file, you need to pass the filename as the third parameter to the program - then, once you finished editing, it will be created and will be available for playback by normal quake executables.
The last parameter is "noedit". Use it only in cases when you don't really want to do any editing, but just to create the output from the input file and the script. It's useful when you want to recreate the output from a modified source using the same script (for example, after demoreleasing the source)


Q: 
I can't move the mouse at all after i've set a camera point, i need to move using keyboard keys before i can use the mouse again
A: 
After setting a camera spot, remstud2 switches to "playback" mode - the demo is presented from the point where camera is at that moment of the demo.
In order to be able to point to different directions, you need to "break free" - by either pressing spacebar (impulse 100), or by moving.


Q: 
What are the client-side commands I can use ?
A:
Your normal keys for movement. 
By default, special remstud2 keys are assigned to mouse, so if you usually use it for movement up and down - I suggest to reassign them to the keyboard.

The new commands are:
+attack - sets a keypoint at camera's current position, angle, and demo's time.
Movements - if you're currently in playback mode, it will switch to roaming mode.
Spacebar (impulse 100) - toggles between roaming and playback
[ (impulse 101) - takes you to the previous key point, and switches to playback mode.
] (impulse 102) - takes you to the next key point, and switches to playback mode.
backspace (impuse 103) - erases the current keypoint (if it exists), and switches to playback mode.
numeric keys 1-7 (impulses 200-206) - playback speed control:
4 (impulse 203) stands for pause,
3 and 5 (202 and 204) move forward and backward one frame
2 and 6 (201 and 205) are more or less standard playback
1 and 7 (200 and 206) are fast forward and rewind.


Q: 
How to make the camera NOT go through the walls when it switches to a new position (a "cut") ?
A: 
It's a little tricky.
First, set a keypoint at the origin point.
Then, move one frame forward (using numeric key 5), and move to the destination position. 
There put another keypoint.
It won't really be a cut, but rather a very fast move - that happens between two frames.

Q: 
I can't see if i'm in the walls or not
A:
Sorry, remstud2 doesn't handle physics, so it can't stop you from going through walls.
Try to use a quake client that makes the screen have a special color when you're in.

Q: 
How do i make the demo go slower? host_framerate didn't have any effect
A:
host_framerate affects how quake server, or quake demo playback work.
But remstud2 isn't using quake server, it's acting as a server on its own - that's why it won't work. Use the numeric keys to control playback speed instead.
Once you finished editing and review the result using normal host_framerate, it will work fine.

Q: 
When I preview a recam while editing, the camera movement seems very jerky.
A:
Quake wasn't designed for something to control your viewing angle continously.
Normally, the server doesn't tell the clients a camera angle - that's while it's not built into normal messages the client receives from the server.
In order for the demos to look ok, they include special camera angles values - but they aren't sent during normal client-server session.
I had to used another message to let the server modify the client's angle during preview - this message is normally used during teleportation, so you'd point in the right direction after teleportation.
This message only allows to have 256 different angles - and as a result, camera angles look a little jerky.
